Updates and onboard storage, in fifteen characters.
Over-the-air updates and onboard data for vehicles that ship with the engine inside.
Vehicles carry more software every year. Every update must arrive exactly.
Vehicles carry more software every year and update over mobile links after they are sold. The engine names each update in fifteen characters, checks the vehicle's right to it, and rebuilds it onboard, bit-exact.
- Typical files
- Updates, maps, onboard data
- What must hold
- Integrity on every vehicle
- Products
- Relay, Safe, Reference designs
- Routes
- Licence the engine, or a sector deal
Send the descriptor. Rebuild the update.
- Updates: software that changes after the car is sold.
- Bandwidth: fleets that update over mobile links.
- Integrity: an update that must arrive bit-exact.
- The update is named by fifteen characters
- Decode checks the vehicle's right to it
- The update regenerates onboard, bit-exact
Where it applies
AutomotiveSent as fifteen characters, rebuilt onboard.
Vehicle data held as strands.
Delivered to the fleet over mobile links.
A royalty per device shipped.
Use cases are examples of where the engine applies, not current deployments.
Licensed per device.
- 01First
The engine ships inside the vehicle
- 02Then
A royalty per device shipped
- 03Finally
Reference designs to start from
Example scenario, not a customer deployment.
Relay
Safe
Reference designsQuestions from automotive teams
Draft answers. To confirm with product.
Does the engine run inside the vehicle?
That is the model: the engine ships inside the device and is licensed per unit. [Supported ECUs: to confirm with engineering.]
What happens if an update arrives corrupted?
Regenerate rebuilds the update bit-exact, or not at all. [Failure handling: to confirm.]
Are there reference designs for automotive?
[Automotive reference designs: to confirm.]
Build for automotive.
License the engine, or find a sector partner for a transactional deal on implexusdata.io.