Applied Intuition OTA Interview Flashcards

OTA: What problem does OTA solve?

OTA lets a manufacturer update vehicle software remotely instead of requiring every vehicle to come into a service center. It matters because modern vehicles keep changing after they leave the factory.

OTA: Why is vehicle OTA harder than a laptop update?

A vehicle may have many ECUs controlling physical functions, not one general-purpose computer. Compatibility, safe install state, rollback, and validation matter much more.

OTA: What is an ECU?

An ECU is an electronic control unit: a computer/controller inside the vehicle that runs software for a vehicle function like battery management, braking, infotainment, or ADAS.

OTA: Why do multiple ECUs make updates harder?

Different ECUs may have different hardware, software versions, dependencies, and safety requirements. Updating one component can affect another, so ordering and compatibility matter.

OTA: What is firmware?

Firmware is software closely tied to the hardware it controls. In vehicles, ECU-level software is often described as firmware because it directly controls physical components.

OTA: What is an update artifact/package?

The artifact is the actual software file or bundle being delivered and installed, like a firmware image, application binary, or software bundle.

OTA: What is metadata/manifest?

Metadata is information that describes and controls the update: version, target ECU, compatible hardware, dependencies, hash, signature, size, and install rules.

OTA: Why is the update file alone not enough?

The vehicle needs context: whether the package is intended for that vehicle/ECU, whether it is compatible, what version it is, and how to verify it before installing.

OTA: Why does versioning matter?

The system needs to know what software is already installed and whether the vehicle can safely move to the new version. Some vehicles may need intermediate updates first.

OTA: Why does compatibility matter?

Not every vehicle has the same hardware, ECU revision, region, options, or current software version. Sending an incompatible update could break a function or fail installation.

OTA: What are dependencies in OTA?

Dependencies are relationships where one software component needs another component or version to be present first. Example: an ADAS update may require camera ECU firmware to be compatible.

OTA: Download vs installation?

Download means getting the package onto the vehicle. Installation means applying it to the ECU or compute unit. A failed download should not change the running software.

OTA: Why separate download and install?

Downloading is mainly a network/storage problem, while installing changes what the vehicle actually runs. Installation needs stronger safety checks and rollback planning.

OTA: What can happen if install fails halfway?

The ECU may be left with incomplete or corrupt software. The system needs recovery, rollback, or a safe fallback so the vehicle does not become unusable.

OTA: What is rollback?

Rollback is the safety net. If the new version fails to boot or fails health checks, the vehicle needs a path back to a known-good version.

OTA: Why rollback matters in vehicles?

A failed update should not leave the car unusable, especially because the car may be far away from a service center. Rollback limits the damage of a bad install.

OTA: What is A/B partitioning?

The system keeps two software slots. The current version runs from A while the new version installs to B; if B fails, it can boot back into A.

OTA: Does every ECU use A/B partitions?

Not necessarily. A/B is a useful pattern, but hardware storage, cost, ECU design, and safety needs determine the actual recovery strategy.

OTA: What is a TCU?

The telematics control unit is the vehicle’s outside-world connection, often using cellular or Wi-Fi to communicate with backend systems.

OTA: What is a gateway?

A gateway manages communication between internal vehicle networks or domains. It can route update traffic and help coordinate what reaches internal ECUs.

OTA: TCU vs gateway?

The TCU is the outside-world connection; the gateway is the internal traffic manager. They may be separate or combined depending on architecture, but the logical roles differ.

OTA: Why not connect every ECU directly to the cloud?

That would increase cost, complexity, and attack surface. It is cleaner to coordinate external connectivity through vehicle connectivity/gateway components.

OTA: What is an internal vehicle network?

It is how computers inside the vehicle communicate with each other. Conceptually, OTA uses it to get update commands or packages from the connected vehicle side to target ECUs.

OTA: What changes in centralized/zonal architecture?

Software may be consolidated onto fewer high-performance or zonal computers. The backend/fleet logic stays similar, but vehicle-side targets and validation change.

OTA: Distributed ECU vs centralized/zonal OTA?

Distributed ECU systems have many update targets and dependencies. Centralized/zonal systems may reduce target count but increase the importance of validating larger compute units and downstream functions.

OTA: What is the vehicle-side OTA flow?

Check eligibility, download artifact/metadata, verify it, stage it, enter safe install state, install, reboot if needed, run health checks, commit or rollback, report status.

OTA: What is an update agent?

Software on the vehicle or ECU that manages the update process: receiving, staging, verifying, installing, reporting, and potentially rolling back.

OTA: What is a bootloader in this context?

A low-level program that helps boot or flash software